Troubleshooting multiple Publishers
A setup that involves multiple Publishers may cause specific issues. This topic explains how to resolve those issues.
In a multiple-Publisher set up, it may be important to see which Publisher actually picked up a publish transaction. To find this out, check the publish transaction details in the Publishing Queue.
- Local Publisher
-
Your local Publisher service may still be running. If this is true, it is highly likely that it will pick up all or most publish transactions, because Publishers running on other machines need more time to check for new publish transactions. To get the most out of your scaled-out setup, stop the Publisher service running on the Content Manager server itself.
- No fallback Publisher when implementing Publisher affinity
-
If you install separate Publishers on dedicated machines, you can implement publisher affinity, which means that you use the SDL Web MMC Snap-in to configure a specific Publisher instance to pick up specific types of publish transactions:
- You can set up a Publisher dedicated to picking up high-priority publish transactions.
- You can set up a Publisher dedicated to picking up publish transactions from a specific host.
- You can set up a Publisher dedicated to picking up publish transactions of items from a specific Publication.
It does not follow that the dedicated Publisher will pick up such publish transactions, only that it will not pick up any other publish transactions.
In this scenario, you may neglect to but no fallback Publisher to pick up publish transactions that fit neither of the dedicated Publishers' criteria. For example, if you have four Publications called A, B, C and D, and you create two dedicated Publishers for content published from A and B, respectively, you still need a 'none of the above' Publisher to pick up the C and D content.